Prerequisites
Before using Google Cloud SQL for MySQL as an endpoint in a Qlik Replicate task, make sure that the prerequisites outlined below have been met.
Driver setup
Installing the driver on Windows
Install MySQL ODBC Unicode Driver 64-bit version 8.0.32 on the Replicate machine.
Installing the driver on Linux
-
Stop the Replicate service and optionally confirm that it has stopped as described in Replicate server procedures.
- Install MySQL ODBC Unicode Driver 64-bit version 8.0.32 on the Replicate machine.
-
Change the working directory to <Replicate-Install-Dir>/bin.
-
Copy the driver location to the site_arep_login.sh file:
echo "export LD_LIBRARY_PATH=\$LD_LIBRARY_PATH:/usr/lib64" >> site_arep_login.sh
This will add the driver to "LD_LIBRARY_PATH" and update the driver location in the site_arep_login.sh file.
-
Optionally, confirm that the driver location was copied:
cat site_arep_login.sh
-
Make sure that the /etc/odbcinst.ini file contains an entry for MySQL, as in the following example:
[MySQL ODBC 8.0 Unicode Driver]
Driver = /usr/lib64/libmyodbc8w.so
UsageCount = 1
-
Start the Replicate service and optionally confirm that it has started as described in Replicate server procedures.
General prerequisites
In addition to the client prerequisites detailed above, make sure that the following prerequisites have also been met:
- A Google Cloud SQL for MySQL account with the required Security requirements.
-
A Google Cloud SQL for MySQL database with the tables that you want to replicate should be accessible in your network.
The following Google Cloud SQL for MySQL editions are supported:
- Google Cloud SQL for MySQL Community Edition
- Google Cloud SQL for MySQL Standard Edition
- Google Cloud SQL for MySQL Enterprise Edition
- Google Cloud SQL for MySQL Cluster Carrier Grade Edition
- To replicate LOB columns when Google Cloud SQL for MySQL 8 is the target database, set the parameter
sort_buffer_size = 128M
in the MySQL database.
Replicating 4-byte UTF8 emojis
To support replication of 4-byte UTF8 emojis, the target schema character set must be set to utf8mb4.